Methods and related devices for handling random access procedure in bandwidth part switching operation

ABSTRACT

A method for handling a Random Access (RA) procedure in the Bandwidth Part (BWP) switching operation includes: receiving, by a User Equipment (UE), Downlink Control Information (DCI) including a BWP switching indication via a Physical Downlink Control Channel (PDCCH) when the UE performs a first RA procedure on a first BWP; and performing, by the UE, at least one of a plurality of procedures in response to the BWP switching indication. The procedures include: stopping the first RA procedure on the first BWP and initiating a second RA procedure on a second BWP indicated by the BWP switching indication; and ignoring the BWP switching indication to continue with the first RA procedure.

CROSS-REFERENCE TO RELATED APPLICATION(S)

The present application claims the benefit of and priority to aprovisional U.S. Patent Application Ser. No. 62/590,381 filed Nov. 24,2017, entitled “Random Access Procedure in BWP Switch Operation,”Attorney Docket No. US72373 (hereinafter referred to as “US72373application”). The disclosure of the US72373 application is herebyincorporated fully by reference into the present application.

FIELD

The present disclosure generally relates to wireless communication, andmore particularly, to methods and related devices for handling a RandomAccess (RA) procedure in the Bandwidth Part (BWP) switching operation.

BACKGROUND

In the next-generation (e.g., fifth generation (5G) New Radio (NR))wireless network, a concept of BWP is introduced. A BWP is a contiguousset of Physical Resource Blocks (PRBs) on a given carrier. These PRBsmay be selected from a contiguous subset of the common resource blocksfor a given numerology. With the help of the BWP, a User Equipment (UE)may not need to monitor the whole bandwidth of a wideband carrier (e.g.,Absolute Radio-Frequency Channel Number (ARFCN)). As such, the powerconsumption at the UE side may be reduced.

Furthermore, in NR, the UE may switch from one BWP to another BWP when aparticular condition is satisfied. However, such BWP switching operationmay be triggered while an RA procedure is performed (or say, the RAprocedure is “on-going”). For example, a UE may be requested by theNetwork (NW) to switch its current BWP to another one during a preambletransmission.

Thus, there is a need in the art for methods and devices for handlingthe RA procedure in the BWP switching operation.

SUMMARY

The present disclosure is directed to methods and related devices forhandling the RA procedure in a BWP switching operation.

In an aspect of the present disclosure, a UE is provided. The UEincludes one or more non-transitory computer-readable media havingcomputer-executable instructions embodied thereon and at least oneprocessor coupled to the one or more non-transitory computer-readablemedia. The at least one processor is configured to execute thecomputer-executable instructions to: receive Downlink ControlInformation (DCI) including a BWP switching indication via a PhysicalDownlink Control Channel (PDCCH) when performing a first RA procedure ona first BWP; and perform at least one of a plurality of procedures inresponse to the BWP switching indication. The procedures include:stopping the first RA procedure on the first BWP and initiating a secondRA procedure on a second BWP indicated by the BWP switching indication;and ignoring the BWP switching indication to continue with the first RAprocedure.

In another aspect of the present disclosure, a method is provided. Themethod includes: receiving, by a UE, DCI including a BWP switchingindication via a PDCCH when the UE performs a first RA procedure on afirst BWP; and performing, by the UE, at least one of a plurality ofprocedures in response to the BWP switching indication. The proceduresinclude: stopping the first RA procedure on the first BWP and initiatinga second RA procedure on a second BWP indicated by the BWP switchingindication; and ignoring the BWP switching indication to continue withthe first RA procedure.

BRIEF DESCRIPTION OF THE DRAWINGS

Aspects of the exemplary disclosure are best understood from thefollowing detailed description when read with the accompanying figures.Various features are not drawn to scale. Dimensions of various featuresmay be arbitrarily increased or reduced for clarity of discussion.

FIG. 1 shows a flowchart for a method of handling an RA procedure in aBWP switching operation, in accordance with an implementation of thepresent disclosure.

FIG. 2 shows a schematic diagram of the BWP switching operation, inaccordance with an implementation of the present disclosure.

FIG. 3 shows a flowchart for a method of handling an RA procedure in aBWP switching operation, in accordance with an implementation of thepresent disclosure.

FIG. 4 shows a schematic diagram of the BWP switching operation, inaccordance with an implementation of the present disclosure.

FIG. 5 shows a flowchart for a method of handling an RA procedure in aBWP switching operation, in accordance with an implementation of thepresent disclosure.

FIG. 6 shows a schematic diagram of the BWP switching operation, inaccordance with an implementation of the present disclosure.

FIG. 7 shows a flowchart for a method of handling an RA procedure in aBWP switching operation, in accordance with an implementation of thepresent disclosure.

FIG. 8 shows a schematic diagram of the BWP switching operation, inaccordance with an implementation of the present disclosure.

FIG. 9 shows a flowchart for a method of handling an RA procedure in aBWP switching operation, in accordance with an implementation of thepresent disclosure.

FIG. 10 shows a flowchart for a method of handling an RA procedure in aBWP switching operation, in accordance with an implementation of thepresent disclosure.

FIG. 11 shows a flowchart for a method of handling an RA procedure in aBWP switching operation, in accordance with an implementation of thepresent disclosure.

FIG. 12 shows a schematic diagram of the BWP switching operation, inaccordance with an implementation of the present disclosure.

FIG. 13 illustrates a block diagram of a node for wirelesscommunication, in accordance with various aspects of the presentapplication.

DETAILED DESCRIPTION

The following description contains specific information pertaining toexemplary implementations in the present disclosure. The drawings in thepresent disclosure and their accompanying detailed description aredirected to merely exemplary implementations. However, the presentdisclosure is not limited to merely these exemplary implementations.Other variations and implementations of the present disclosure willoccur to those skilled in the art. Unless noted otherwise, like orcorresponding elements among the figures may be indicated by like orcorresponding reference numerals. Moreover, the drawings andillustrations in the present disclosure are generally not to scale, andare not intended to correspond to actual relative dimensions.

For the purpose of consistency and ease of understanding, like featuresare identified (although, in some examples, not shown) by numerals inthe example figures. However, the features in different implementationsmay be differed in other respects, and thus shall not be narrowlyconfined to what is shown in the figures.

References to “one implementation,” “an implementation,” “exampleimplementation,” “various implementations,” “some implementations,”“implementations of the present application,” etc., may indicate thatthe implementation(s) of the present application so described mayinclude a particular feature, structure, or characteristic, but notevery possible implementation of the present application necessarilyincludes the particular feature, structure, or characteristic. Further,repeated use of the phrase “in one implementation,” or “in an exampleimplementation,” “an implementation,” do not necessarily refer to thesame implementation, although they may. Moreover, any use of phraseslike “implementations” in connection with “the present application” arenever meant to characterize that all implementations of the presentapplication must include the particular feature, structure, orcharacteristic, and should instead be understood to mean “at least someimplementations of the present application” includes the statedparticular feature, structure, or characteristic. The term “coupled” isdefined as connected, whether directly or indirectly through interveningcomponents, and is not necessarily limited to physical connections. Theterm “comprising,” when utilized, means “including, but not necessarilylimited to”; it specifically indicates open-ended inclusion ormembership in the so-described combination, group, series and theequivalent.

Additionally, for the purposes of explanation and non-limitation,specific details, such as functional entities, techniques, protocols,standard, and the like are set forth for providing an understanding ofthe described technology. In other examples, detailed description ofwell-known methods, technologies, system, architectures, and the likeare omitted so as not to obscure the description with unnecessarydetails.

Persons skilled in the art will immediately recognize that any networkfunction(s) or algorithm(s) described in the present disclosure may beimplemented by hardware, software or a combination of software andhardware. Described functions may correspond to modules may be software,hardware, firmware, or any combination thereof. The softwareimplementation may comprise computer executable instructions stored oncomputer readable medium such as memory or other type of storagedevices. For example, one or more microprocessors or general purposecomputers with communication processing capability may be programmedwith corresponding executable instructions and carry out the describednetwork function(s) or algorithm(s). The microprocessors or generalpurpose computers may be formed of applications specific integratedcircuitry (ASIC), programmable logic arrays, and/or using one or moredigital signal processor (DSPs). Although some of the exampleimplementations described in this specification are oriented to softwareinstalled and executing on computer hardware, nevertheless, alternativeexample implementations implemented as firmware or as hardware orcombination of hardware and software are well within the scope of thepresent disclosure.

The computer readable medium includes but is not limited to randomaccess memory (RAM), read only memory (ROM), erasable programmableread-only memory (EPROM), electrically erasable programmable read-onlymemory (EEPROM), flash memory, compact disc read-only memory (CD ROM),magnetic cassettes, magnetic tape, magnetic disk storage, or any otherequivalent medium capable of storing computer-readable instructions.

A radio communication network architecture (e.g., a long term evolution(LTE) system, an LTE-Advanced (LTE-A) system, or an LTE-Advanced Prosystem) typically includes at least one base station, at least one UE,and one or more optional network elements that provide connectiontowards a network. The UE communicates with the network (e.g., a CN, anevolved packet core (EPC) network, an Evolved Universal TerrestrialRadio Access network (E-UTRAN), a Next-Generation Core (NGC), or aninternet) through a radio access network (RAN) established by the basestation.

It should be noted that, in the present application, a UE may include,but is not limited to, a mobile station, a mobile terminal or device, auser communication radio terminal, etc. For example, a UE may be aportable radio equipment, which includes, but is not limited to, amobile phone, a tablet, a wearable device, a sensor, or a personaldigital assistant (PDA) with wireless communication capability. The UEis configured to receive/transmit signals over an air interface from/toone or more cells in a radio access network.

A base station may include, but is not limited to, a node B (NB) as inthe UMTS, an evolved node B (eNB) as in the LTE-A, a radio networkcontroller (RNC) as in the UMTS, a base station controller (BSC) as inthe GSM/GERAN, an NG-eNB as in an E-UTRA base station in connection withthe SGC, a next generation node B (gNB) as in the 5G-AN, and any otherapparatus capable of controlling radio communication and managing radioresources within a cell. The base station may connect to serve the oneor more UEs through a radio interface to the network.

A base station may be configured to provide communication servicesaccording to at least one of the following radio access technologies(RATs): Worldwide Interoperability for Microwave Access (WiMAX), GlobalSystem for Mobile communications (GSM, often referred to as 2G), GSMEDGE radio access Network (GERAN), General Packet Radio Service (GRPS),Universal Mobile Telecommunication System (UMTS, often referred to as3G) based on basic wideband-code division multiple access (W-CDMA),high-speed packet access (HSPA), LTE, LTE-A, eLTE (evolved LTE), NewRadio (NR, often referred to as 5G), and/or LTE-A Pro. However, thescope of the present application should not be limited to the abovementioned protocols.

The base station is operable to provide radio coverage to a specificgeographical area using a plurality of cells forming the radio accessnetwork. The base station supports the operations of the cells. Eachcell is operable to provide services to at least one UE within its radiocoverage. More specifically, each cell (often referred to as a servingcell) provides services to serve one or more UEs within its radiocoverage, (e.g., each cell schedules the downlink and optionally uplinkresources to at least one UE within its radio coverage for downlink andoptionally uplink packet transmissions). The base station cancommunicate with one or more UEs in the radio communication systemthrough the plurality of cells. A cell may allocate sidelink (SL)resources for supporting proximity service (ProSe). Each cell may haveoverlapped coverage areas with other cells.

As discussed above, the frame structure for NR is to support flexibleconfigurations for accommodating various next generation (e.g., 5G)communication requirements, such as enhanced mobile broadband (eMBB),massive machine type communication (mMTC), ultra-reliable communicationand low latency communication (URLLC), while fulfilling highreliability, high data rate and low latency requirements. The orthogonalfrequency-division multiplexing (OFDM) technology as agreed in 3GPP mayserve as a baseline for NR waveform. The scalable OFDM numerology, suchas the adaptive sub-carrier spacing, the channel bandwidth, and theCyclic Prefix (CP), may also be used. Additionally, two coding schemesare considered for NR: (1) low-density parity-check (LDPC) code and (2)Polar Code. The coding scheme adaption may be configured based on thechannel conditions and/or the service applications.

Moreover, it should be noted that in a transmission time interval TX ofa single NR frame, at least downlink (DL) transmission data, a guardperiod, and uplink (UL) transmission data should be included.Additionally, the respective portions of the DL transmission data, theguard period, and the UL transmission data should also be configurable,for example, based on the network dynamics of NR. In addition, sidelinkresource may also be provided in an NR frame to support ProSe services.

In addition, the terms “system” and “network” herein may be usedinterchangeably. The term “and/or” herein is only an associationrelationship for describing associated objects, and represents thatthree relationships may exist. For example, A and/or B may indicatethat: A exists alone, A and B exist at the same time, and B existsalone. In addition, the character “I” herein generally represents thatthe former and latter associated objects are in an “or” relationship.

In LTE, for a connected UE, the RA procedure may be performed for atleast the following events related to the Primary Cell (PCell):

-   -   1. Downlink (DL) data arrival during RRC_CONNECTED requiring an        RA procedure, e.g., when the Uplink (UL) synchronization status        is “non-synchronized.”    -   2. UL data arrival during RRC_CONNECTED requiring an RA        procedure, e.g., when the UL synchronization status is        “non-synchronized” or no Physical Uplink Control Channel (PUCCH)        resources for Scheduling Request (SR) are available.    -   3. For positioning purpose during RRC_CONNECTED requiring an RA        procedure, e.g., when timing advance is needed for UE        positioning.

The RA procedure takes two distinct forms: Contention-Based RA (CBRA)and contention-free RA (CFRA). The CBRA procedure may be a four-stepprocedure in which the RA preamble (msg1) is transmitted on the RandomAccess Channel (RACH) in UL, the Random Access Response (RAR) (msg2) isgenerated by the Medium Access Control (MAC) entity and transmitted onthe Downlink Shared Channel (DL-SCH), the first scheduled UL data (msg3)is transmitted on the Uplink Shared Channel (UL-SCH), and the contentionresolution (msg4) is transmitted in DL. On the other hand, the CFRAprocedure may be a three-step procedure in which the RA preambleassignment is transmitted via a dedicated signaling in DL, the RApreamble is transmitted on the RACH in UL, and the RAR is transmitted onDL-SCH.

For the CBRA procedure, the RA preamble is selected by the UE's MACentity and transmitted to the NW (e.g., a base station) on thepre-configured common RA resources (or common Physical Random AccessChannel (PRACH) resources/occasions). After the preamble transmission,the UE's MAC entity may monitor the Physical Downlink Control Channel(PDCCH) in the common search space for RAR(s) identified by the RA-RadioNetwork Temporary Identifier (RA-RNTI) within a configured RAR window.The RA-RNTI may be calculated by a pre-defined formula associated withthe time and frequency of the RA resource on which the RA preamble istransmitted. For example, the RAR window may start at the subframe thatcontains the end of the last preamble repetition plus three subframesand have the length of a configured RAR window size. The UE's MAC entitymay stop monitoring the RAR(s) after successfully receiving an RARcontaining the RA preamble identifier(s) that matches the transmitted RApreamble. If no RAR is received in the corresponding the RAR window, ornone of the received RARs contains the RA preamble identifiercorresponding to the transmitted RA preamble, the RAR reception may beconsidered not successful and the UE may start transmitting the next RApreamble.

In NR, as in LTE, after transmitting the RA preamble, the UE may monitorthe RAR(s) in an RAR window. The RAR window may start with a fixedduration from the end of the RACH transmission occasion and the size ofthe RAR window is configurable. The RAR reception may be deemedsuccessful if the received RAR corresponds to both the RA preambletransmitted by the UE and the RACH resource in which the UE transmitsthe RA preamble. Moreover, as in LTE, the RA procedure may be performedon the PCell as well as the Secondary Cell (SCell). Only the CFRAprocedure can be performed on the SCell (other than the Primary SCell(PSCell)). The RA procedure for the SCell (other than the PSCell) isonly initiated by the NW. When performing the RA procedure on the PCellwhile Carrier Aggregation (CA) is configured, the UE may transmit the RApreamble to the PCell and receive the corresponding RAR from the PCell.When performing the CFRA procedure on the SCell while CA is configured,the UE may transmit the RA preamble to the SCell and receive thecorresponding RAR from the PCell. When performing the RA procedure onthe PCell or the PSCell while Dual-Connectivity (DC) is configured, theUE may transmit the RA preamble and receive the RAR on the correspondingcell. When performing the CFRA procedure on the SCell (other than thePSCell) while DC is configured, the UE may transmit the RA preamble onthe SCell and receive the corresponding RAR on the PCell in the MasterCell Group (MCG) and the PSCell in the Secondary Cell Group (SCG).

Furthermore, in NR, there may be multiple beams at a higher frequency.For the RA procedure, the UE's MAC entity may need to know the selectedSynchronization Signal (SS) block (which may be used to identify acorresponding beam) to select the associated PRACH resource and/or theassociated preamble sequences. A selected SS block may be provided bythe Layer 1 (L1) to the MAC entity.

For each UE-specific serving cell, one or more DL BWPs and one or moreUL BWPs may be configured for a UE through a dedicated Radio ResourceControl (RRC) signaling. However, for a UE, there is at most one activeDL BWP and at most one active UL BWP at a given time for a serving cell.To switch among different BWPs of a serving cell, in NR, the NW maytrigger a BWP switching operation to switch the UE's active BWP from oneBWP to another (of the same link direction) via a single scheduling DCI.Furthermore, a timer-based solution may be used to switch the active DLBWP to the default BWP. For example, in NR, once a BWP inactivity timerexpires, the UE may switch the active BWP to a default BWP configured bythe NW. Moreover, for each serving cell, the maximal number of DL/UL BWPconfigurations may be:

-   -   1. For paired spectrum: 4 DL BWPs and 4 UL BWPs.    -   2. For unpaired spectrum: 4 DL/UL BWP pairs.    -   3. For Supplementary uplink (SUL): 4 UL BWPs.

For paired spectrum, a dedicated timer for timer-based active DL BWPswitching to the default DL BWP is supported:

-   -   1. A UE starts the timer when it switches its active DL BWP to a        DL BWP other than the default DL BWP.    -   2. A UE restarts the timer to the initial value when it        successfully decodes a DCI to schedule PDSCH(s) in its active DL        BWP.    -   3. A UE switches its active DL BWP to the default DL BWP when        the timer expires.

For unpaired spectrum, a dedicated timer for timer-based active DL/ULBWP pair switching to the default DL/UL BWP pair is supported:

-   -   1. A UE starts the timer when it switches its active DL/UL BWP        pair to a DL/UL BWP pair other than the default DL/UL BWP pair.    -   2. A UE restarts the timer to the initial value when it        successfully decodes a DCI to schedule PDSCH(s) in its active        DL/UL BWP pair.    -   3. A UE switches its active DL/UL BWP pair to the default DL/UL        BWP pair when the timer expires.

The BWP switching operation may be triggered when the RA procedure ison-going. For example, when the UE is performing the RA preambletransmission on the active UL BWP, the BWP switching operation may betriggered by the NW (e.g., the NW transmits a BWP switching indicationvia an L1 signaling), or a specific timer (e.g., the UE autonomouslyswitches back to the default BWP after the BWP inactivity timerexpires). In such a case, the RA procedure and the UE behavior may beaffected due to the BWP switching operation. For example, in LTE or NR,the SR procedure is used for requesting UL-SCH resources for a newtransmission. If there is a pending SR, the UE may initiate an RAprocedure and cancel all pending SR(s) if the MAC entity has no validPUCCH resource for the configured SR (e.g., Dedicated-SR (D-SR)resources).

In various implementations of the present disclosure, when performing anRA procedure on a BWP, the UE may perform at least one of a plurality ofprocedures in response to a BWP switching indication received from theNW, based on UE implementation (e.g., decided by the UE itself),pre-configuration, or pre-defined rules. The plurality of procedures mayinclude: (1) continuing with the RA procedure on another BWP, (2)stopping/aborting the RA procedure and initiating a new RA procedure onanother BWP, (3) performing an SR procedure on another BWP, (4) ignoringthe BWP switching indication and continuing with the RA procedure on theoriginal active BWP, and (5) ignoring the BWP switching indication andcontinuing with the RA procedure on an initial BWP indicated by thesystem information from the NW (e.g., a base station). In someimplementations, the NW may inform the UE (e.g., via the systeminformation or a dedicated signaling) of whether the BWP switchingoperation is allowed to be performed during an on-going RA procedure.The UE may use such information to decide which procedure(s) should beperformed in response to the BWP switching indication.

For better comprehension, details of the various procedures aredescribed with reference to FIGS. 1 through 10.

FIG. 1 shows a flowchart for a method of handling an RA procedure in aBWP switching operation, in accordance with an implementation of thepresent disclosure. As shown in FIG. 1, the flowchart includes actions102, 104 and 106.

In action 102, the UE initiates an RA procedure on a first BWP.

In action 104, the UE receives DCI from the NW (e.g., a base station)via a PDCCH when performing the RA procedure on the first BWP. The DCIincludes a BWP switching indication for switching the first BWP to asecond BWP.

In action 106, the UE continues with the RA procedure on the second BWP.For example, the UE may continue with the RA procedure on the second BWPby using a group of RA parameters (e.g., the initial RA preamble power(e.g., preambleReceivedTargetPower), the power-ramping factor (e.g.,powerRampingStep), and/or the maximum number of RA preamble transmission(e.g., preambleTransMax)) with configured values and a group of UEvariables (e.g., the preamble counter (e.g.,PREAMBLE_TRANSMISSION_COUNTER) and/or the power ramping counter (e.g.,PREAMBLE_POWER_RAMPING_COUNTER)) with successive/non-reset values (e.g.,counter values).

In the present implementation, the first BWP may refer to a previousUL/DL active BWP, and the second BWP may refer to a current UL/DL activeBWP.

According to FIG. 1, the UE (or the UE's MAC entity) may continue withthe on-going RA procedure on the second BWP based on UE implementation,pre-configuration, or pre-defined rules (e.g., the RA procedure is forUL synchronization). It should be noted that for a paired spectrumscenario, the BWP switching indication may mean to switch the DL BWP,but the UL BWP may remain the same or not, and vice versa. For anun-paired spectrum scenario, the BWP switching indication may mean toswitch both the DL BWP and UL BWP.

In some implementations, the UE may stop/abort a part of the on-going RAprocedure on the first BWP (e.g., the waiting for the corresponding RAR,the transmission of msg3, or the waiting for the corresponding msg4 onthe first BWP), and send another new preamble on the RA resourcesconfigured on the second BWP. Since the RA procedure is on-going, thenumber of RA preamble transmissions and/or power ramping steps may beincreased. In another implementation, the number of preambletransmissions and/or power ramping steps may not be increased. Forexample, the RA preamble(s) sent on the RA resources configured on theprevious UL BWP may not be counted, and/or the power ramping operationmay not be executed.

In some implementations, the UE may continue with the on-going RAprocedure if the current active UL BWP and the previous UL BWP aresynchronized. For example, the UE may determine whether the currentactive UL BWP and the previous UL BWP are synchronized based on thepre-configuration (e.g., the current active UL BWP and the previous ULBWP are in the same timing advance group). The NW may indicate whichBWP(s) belongs to which timing advance group via an RRC signaling. TheNW may transmit all of the corresponding RAR(s) (or msg3) on all or someof the existing DL BWP(s), and the UE may just need to monitor thecommon search space in the current active DL BWP.

In some implementations, the UE may monitor the common search spaces ofboth the current active DL BWP and the previous DL BWP for receiving thecorresponding RAR (or msg4), in a case that the preamble (or msg3) istransmitted on the previous UL BWP, the UE switches to the currentactive UL BWP, and the UE still waits for the corresponding RAR (ormsg4).

In some implementations, for a UE which transmits the msg3 on UL BWP #1and switches to UL BWP #2 after transmitting the msg3, the UE maymonitor the corresponding msg4 on the current active DL BWP before thecontention resolution timer expires.

In some implementations, the NW may transmit the corresponding RAR (ormsg4) on the DL BWP associated with the UL BWP which receives the RApreamble (or msg3) from the UE. For example, for a UE which transmits apreamble on UL BWP #1 and switches to UL BWP #2 after transmitting thepreamble, the UE may not receive the corresponding RAR from the CORESETof the DL BWP associated with UL BWP #2 within the RAR window. The UEmay then try to send another preamble on the RA resources configured forUL BWP #2 for continuing with the RA procedure. For another example, fora UE which transmits the msg3 on UL BWP #1 and switches to UL BWP #2after transmitting the msg3, the UE may not receive the correspondingmsg4 before the contention resolution timer expires. In such a case, theUE may consider the contention resolution is not successful and try tosend another RA preamble on the RA resources configured for UL BWP #2 tocontinue with the RA procedure.

In some implementations, the UE may receive the RAR on DL BWP #1 andswitches to UL BWP #2 before transmitting the corresponding msg3. The ULBWP #2 may be different from the DL BWP #1's pairing UL BWP. If the ULgrants indicated by the RAR is transmitted on a UL BWP (e.g., the DL BWP#1's pairing UL BWP) other than UL BWP #2, or not valid in UL BWP #2,the UE may switch back to a BWP which has the corresponding UL grantsfor the msg3 transmission, and wait for the msg4 on the associated DLBWP. The NW may not know that the UE has switched to the BWP on whichthe UL grants indicated by the RAR are for the msg3 transmission.Therefore, some DL data transmission may be missed by the UE, and the NWmay need to send another DCI for BWP switching to control the UE again.For another example, the UE may not transmit the msg3 for contentionresolution if the UL grants indicated by the RAR are on a UL BWP (e.g.,UL BWP #1) other than UL BWP #2, or not valid in the current active ULBWP (e.g., UL BWP #2). In such a case, the UE may determine that thecontention resolution is not successful, and the UE may try to sendanother RA preamble on the RA resources configured in UL BWP #2 forcontinuing the RA procedure.

In some implementations, the UE performs action 106 when certaincondition(s) is satisfied. For example, the condition may be that thesecond BWP is configured with RA resource(s) and D-SR resource(s). Asanother example, the condition may be that the second BWP is configuredwith RA resource(s) but no D-SR resource(s). In such cases, the UE may,for example, determine whether to enter action 106 by checking whetherthe second BWP indicated by the DCI is configured with (sufficient) RAresources and/or D-SR resources, depending on UE implementation,pre-configuration or ore-defined rules.

FIG. 2 shows a schematic diagram of the BWP switching operation, inaccordance with an implementation of the present disclosure. As shown inFIG. 2, the UE first initiates an RA procedure on the BWP 22 at timeT202, and then receives DCI from the NW (e.g., a base station) at timeT204 while the RA procedure is on-going. The DCI includes, for example,a BWP switching indication for switching UE's active BWP to the BWP 24.

In response to the BWP switching indication, the UE switches from theBWP 22 to the new indicated BWP 24 at time T206, and continues with theRA procedure on the BWP 24. In some implementations, the BWP 24 may beconfigured with both RA resources and D-SR resources. In someimplementations, the BWP 24 may be configured with RA resources but noD-SR resources.

Because in NR the UE may have at most one active DL BWP and at most oneactive UL BWP at a given time for a serving cell, after the UE switchesfrom the BWP 22 to the BWP 24 at time T206, the BWP 22 enters aninactive period, while the BWP 24 becomes active, as shown in FIG. 2.

FIG. 3 shows a flowchart for a method of handling an RA procedure in aBWP switching operation, in accordance with an implementation of thepresent disclosure. As shown in FIG. 3, the flowchart includes actions302, 304 and 306.

In action 302, the UE initiates an RA procedure on a first BWP.

In action 304, the UE receives DCI from the NW (e.g., a base station)via a PDCCH when performing the RA procedure on the first BWP. The DCIincludes a BWP switching indication for switching the first BWP to asecond BWP.

In action 306, the UE stops the RA procedure on the first BWP, andinitiates a new RA procedure on the second BWP indicated by the DCI. Forexample, the UE may perform the newly initiated RA procedure on thesecond BWP by using a group of RA parameters (e.g., the initial RApreamble power (e.g., preambleReceivedTargetPower), the power-rampingfactor (e.g., powerRampingStep), and/or the maximum number of RApreamble transmission (e.g., preambleTransMax)) with configured valuesand a group of UE variables (e.g., the preamble counter (e.g.,PREAMBLE_TRANSMISSION_COUNTER) and/or the power ramping counter (e.g.,PREAMBLE_POWER_RAMPING_COUNTER)) with reset values.

In the present implementation, the first BWP may refer to a previousUL/DL active BWP, and the second BWP may refer to a current active UL/DLBWP.

According to FIG. 3, the UE (or the UE's MAC entity) may stop/abort theon-going RA procedure on the first BWP and initiate a new RA procedureon the second BWP. For example, the UE may transmit a new preamble onthe RA resources configured on the second BWP and start counting thenumber of preamble transmissions all over again. Such a new preamble maybe, for example, the first one preamble for the new RA procedure.

In some implementations, in response to the BWP switching indication,the UE may decide to continue with the on-going RA procedure (e.g., theprocedure in FIG. 1), or abort the on-going RA procedure and initiate anew RA procedure on the newly indicated BWP (e.g., the procedure in FIG.3) based on UE implementation, pre-configuration, or pre-defined rules.For example, the pre-configuration may be provided to the UE via an RRCmessage (e.g., an RRC reconfiguration message) to indicate to the UE howto respond to the BWP switching indication. The RRC message may or maynot include the PRACH configuration for the newly initiated RA procedureon the indicated BWP (e.g., the second BWP). The pre-define rules may bedetermined based on the numerology for different service types, or basedon whether the current active UL BWP and the previous UL BWP aresynchronized.

If the RRC message (e.g., the RRC reconfiguration message) thatindicates the UE to follow the procedure of FIG. 3 (e.g., initiating anew RA procedure on the indicated BWP) does not include the PRACHconfiguration for the new RA procedure, the UE, by default, may apply acommon PRACH configuration. The common PRACH configuration may beprovided by the Remaining Minimum System Information (RMSI). In NR, theminimum system information can be divided into two parts. The first partof the minimum system information is put in the Physical BroadcastChannel (PBCH), and the second part is the RMSI. The first part of theminimum system information may contain at least one of: the System FrameNumber (SFN), the scheduling of the RMSI, the “cellBarred” InformationElement (IE), and the “intraFreqReselection” IE. The IE “cellBarred” maycorrespond to the information for quickly identifying the UE that isbared from camping on the cell. The IE “intraFreqReselection” mayindicate whether the UE excludes the cells on the same frequency as acandidate for cell selection/reselection for a certain period of timewhen the cell status in indicated as “barred.” On the other hand, theRMSI may include a common RACH configuration and the schedulinginformation of each system information message that contains a set ofsystem information blocks.

In some implementations, each BWP configuration may include anassociated PRACH configuration, and the UE may follow the information(e.g., RA resources) if the RA procedure on that BWP is expected to beproceeded. Moreover, the RRC message (e.g., the RRC reconfigurationmessage) may further indicate that the new RA procedure is to beexecuted on the initial BWP or the default BWP. The base station (e.g.,gNB) may make such a decision based on, for example, the timing advancegroup information.

In some implementations, the UE performs action 306 when certaincondition(s) is satisfied. For example, the condition may be that thesecond BWP is configured with RA resource(s) and D-SR resource(s). Asanother example, the condition may be that the second BWP is configuredwith RA resource(s) but no D-SR resource(s). In such cases, the UE maydetermine whether to enter action 306 by checking whether the second BWPindicated by the DCI is configured with (sufficient) RA resources and/orD-SR resources, depending on UE implementation, pre-configuration orore-defined rules.

FIG. 4 shows a schematic diagram of the BWP switching operation, inaccordance with an implementation of the present disclosure. As shown inFIG. 4, the UE first initiates an RA procedure on the BWP 42 at timeT402, and then receives DCI for BWP switching from the NW (e.g., a basestation) at time T404 while the RA procedure is on-going. After that,the UE switches to the BWP 44 indicated by the DCI at time T406, andinitiates a new RA procedure on the indicated BWP 44. In someimplementations, the BWP 44 may be configured with both RA resources andD-SR resources. In some implementations, the BWP 44 may be configuredwith RA resources but no D-SR resources.

Because in NR the UE may have at most one active DL BWP and at most oneactive UL BWP at a given time for a serving cell, after the UE switchesfrom the BWP 42 to the BWP 44 at time T406, the BWP 42 enters aninactive period, while the BWP 44 becomes active, as shown in FIG. 4.

FIG. 5 shows a flowchart for a method of handling an RA procedure in aBWP switching operation, in accordance with an implementation of thepresent disclosure. As shown in FIG. 5, the flowchart includes actions502, 504 and 506.

In action 502, the UE initiates an RA procedure on a first BWP.

In action 504, the UE receives DCI from the NW (e.g., a base station)via a PDCCH when performing the RA procedure on the first BWP. The DCIincludes a BWP switching indication for switching the first BWP to asecond BWP configured with D-SR resource(s).

In action 506, the UE performs an SR procedure on the second BWP.

In the present implementation, the first BWP may refer to a previousUL/DL active BWP, and the second BWP may refer to a current UL/DL activeBWP.

According to FIG. 5, the UE (or the UE's MAC entity) may stop/abort theon-going RA procedure based on UE implementation, pre-configuration, orpre-defined rules (e.g., the RA procedure is for UL transmission), andinitiate an SR procedure on the second BWP configured with D-SRresources.

In some implementations, the UE performs action 506 when certaincondition(s) is satisfied. For example, the condition may be that thesecond BWP is configured with RA resource(s) and D-SR resource(s). Asanother example, the condition may be that the second BWP is configuredwith D-SR resource(s) but no RA resources. In such cases, the UE maydetermine whether to enter action 506 by checking whether the second BWPindicated by the DCI is configured with (sufficient) RA resources and/orD-SR resources, depending on UE implementation, pre-configuration orore-defined rules.

FIG. 6 shows a schematic diagram of the BWP switching operation, inaccordance with an implementation of the present disclosure. As shown inFIG. 6, the UE first initiates an RA procedure on the BWP 62 at timeT602, and then receives DCI for BWP switching from the NW (e.g., a basestation) at time T604 while the RA procedure is on-going. The DCI mayinclude a BWP switching indication for switching UE's active BWP to theBWP 64.

In response to the BWP switching indication, the UE switches to the BWP64 at time T606, and initiates an SR procedure on the BWP 64. In someimplementations, the BWP 64 may be configured with both RA resources andD-SR resources. In some implementations, the BWP 44 may be configuredwith D-SR resources but no RA resources.

Because in NR the UE may have at most one active DL BWP and at most oneactive UL BWP at a given time for a serving cell, after the UE switchesfrom the previous BWP 62 to the new BWP 64 at time T606, the BWP 62enters an inactive period, while the BWP 64 become active, as shown inFIG. 6.

FIG. 7 shows a flowchart for a method of handling an RA procedure in aBWP switching operation, in accordance with an implementation of thepresent disclosure. As shown in FIG. 7, the flowchart includes actions702, 704 and 706.

In action 702, the UE initiates an RA procedure on a first BWP.

In action 704, the UE receives DCI from the NW (e.g., a base station)via a PDCCH when performing the RA procedure on the first BWP. The DCImay include a BWP switching indication for switching the first BWP to asecond BWP.

In action 706, the UE ignores the BWP switching indication and continueswith the on-going RA procedure on the first BWP.

According to FIG. 7, the UE (or the UE's MAC entity) may continue withthe RA procedure on the first BWP, based on UE implementation,pre-configuration, or pre-defined rules (e.g., the RA procedure is forUL synchronization).

In some implementations, the UE may ignore the BWP switching indicationand stop the BWP inactivity timer. The BWP inactivity timer may berestarted by the UE when the UE decides to execute the BWP switchingoperation (e.g., switching from the first BWP to a non-default BWP, suchas the second BWP). In addition, the UE's MAC entity may inform thePhysical Layer (PHY) entity to ignore the DCI while the RA procedure isinitiated. The UE's MAC entity may also inform the PHY entity that theRA procedure is successfully completed, so that the PHY entity canexecute the DCI again.

In some implementations, if the RA procedure fails (e.g., the value ofthe preamble counter exceeds a threshold), the UE's MAC entity mayindicate an RA problem to the upper layer, and the UE may then switchback to the default BWP. For example, the threshold is the maximumnumber of RA preamble transmission.

In some implementations, the UE performs action 706 when certaincondition(s) is satisfied. For example, the condition may be that thesecond BWP is configured with RA resource(s) and D-SR resource(s). Asanother example, the condition may be that the second BWP is configuredwith RA resource(s) but no D-SR resource(s). As another example, thecondition may be that the second BWP is configured with D-SR resource(s)but no RA resource(s). As another example, the condition may be that thesecond BWP is configured with no D-SR resource(s) and no RA resource(s).

FIG. 8 shows a schematic diagram of the BWP switching operation, inaccordance with an implementation of the present disclosure. As shown inFIG. 8, the UE first initiates an RA procedure on the BWP 82 at timeT802, and then receives DCI from the NW (e.g., a base station) at timeT804 while the RA procedure is on-going. The DCI may include, forexample, a BWP switching indication for switching the BWP 82 to the BWP84. In the present implementation, the BWP 84 may be configuredwith/without RA resources.

In response to the reception of the DCI, the UE may ignore the BWPswitching indication, and continue with the RA procedure on the BWP 82.

FIG. 9 shows a flowchart for a method of handling RA procedure in BWPswitching operation, in accordance with an implementation of the presentdisclosure. As shown in FIG. 9, the flowchart includes actions 902, 904and 906. The main difference between the flowchart of FIG. 7 and theflowchart of FIG. 9 is that after ignoring the BWP switching indicationin the DCI, the UE (or the UE's MAC entity) may continue with theon-going RA procedure on an initial BWP indicated by the systeminformation from the NW (e.g., a base station), instead of the BWPindicated by the DCI.

As shown in action 902, the UE initiates an RA procedure on a first BWP.

In action 904, the UE receives DCI from the NW (e.g., a base station)via a PDCCH when performing the RA procedure on the first BWP. The DCIincludes a BWP switching indication for switching the first BWP to asecond BWP.

In action 906, the UE ignores the BWP switching indication and continueswith the on-going RA procedure on an initial BWP other than the secondBWP. Information of the initial BWP may be transmitted by the NW via thesystem information.

FIG. 10 shows a flowchart for a method of handling an RA procedure in aBWP switching operation, in accordance with an implementation of thepresent disclosure. As shown in FIG. 10, the flowchart includes actions1002, 1004 and 1006.

In action 1002, the UE switches to a BWP configured with RA resources.

In action 1004, the UE initiates an RA procedure.

In action 1006, the UE performs the BWP switching operation when the RAprocedure is successfully completed.

In some implementations, when the RA procedure is on-going, the UE (orthe UE's MAC entity) may autonomously switch back to a pre-configured orpre-defined BWP (e.g., the default BWP or the initial BWP) or any BWPconfigured with RA resources for performing the RA procedure. In such acase, the UE's MAC entity may inform the PHY entity to switch to thetarget BWP while the RA procedure is initiated. The UE's MAC entity mayfurther inform the PHY entity that the RA procedure is successfullycompleted, so that the PHY entity may execute the DCI for BWP switchingagain. The BWP inactivity timer may be stopped in this case. The UE mayrestart the BWP inactivity timer when the UE executes the BWP switchingoperation to a non-default BWP (e.g., the second BWP indicated by theDCI).

In some implementations, if the RA procedure fails (e.g., the value ofthe preamble counter exceeds a threshold), the UE's MAC entity mayindicate an RA problem to the upper layer, and the UE may initiate anRRC connection re-establishment procedure, or switch back to the defaultBWP. For example, the threshold is the maximum number of RA preambletransmission.

In some implementations, the UE may monitor both the CORESET (or PDCCH)of the active BWP (which the NW indicates to use through the DCI) andthe target BWP (on which the UE is performing the RA procedure). The UEmay stop the BWP inactivity timer in this case, and restart the BWPinactivity timer when executing the DCI to switch to the non-defaultBWP.

In some implementations, when the RA procedure is on-going, the UE (orthe UE's MAC entity) may continue the on-going RA procedure on theprevious active (DL/UL) BWP based on UE implementation,pre-configuration or pre-defined rules (e.g., the RA procedure is for ULsynchronization). The UE may ignore the BWP switching indication in theDCI and stop the BWP inactivity timer in this case. The UE may restartthe BWP inactivity timer when the UE executes the BWP switchingoperation in response to the DCI to switch to a non-default BWP. TheUE's MAC entity may inform the PHY entity to ignore the DCI while the RAprocedure is initiated. The UE's MAC entity may also inform the PHYentity that the RA procedure is successfully completed, so that the PHYentity may execute the DCI command again.

FIG. 11 shows a flowchart of a method for handling RA procedure in BWPswitching operation, in accordance with an implementation of the presentdisclosure. As shown in FIG. 11, the flowchart includes actions 1102,1104 and 1106.

In action 1102, the UE initiates an RA procedure on a first BWP.

In action 1104, the UE receives DCI from the NW (e.g., a base station)via a PDCCH when performing the RA procedure on the first BWP. The DCImay include a BWP switching indication for switching the first BWP to asecond BWP.

In action 1106, the UE initiates a new RA procedure on an initial BWPindicated by the system information from the NW (e.g., a base station)because the second BWP is not configured with (valid) RA resources.

In the present implementation, the UE may switch to the second BWP inresponse to the received DCI. After that, if the UE finds that thesecond BWP does not have RA resources for performing the RA procedure,the UE may then switch back to the initial BWP which is configured withRA resource(s), and initiate a new RA procedure on the initial BWP.

FIG. 12 shows a schematic diagram of the BWP switching operation, inaccordance with an implementation of the present disclosure. As shown inFIG. 12, the UE first initiates an RA procedure on the BWP 1202 at timeT1202, and then receives DCI from the NW (e.g., a base station) at timeT1204 while the RA procedure is on-going. The DCI may include, forexample, a BWP switching indication for switching the BWP 1202 to theBWP 1204.

At time T1206, the UE switches to the BWP 1204 according to the DCI butfinds that the BWP 1204 is not configured with (valid) RA resources.Then, at time T1208, the UE autonomously switch back to an initial BWPindicated 1206 by the system information from the NW (e.g., a basestation). At time T1210, the UE initiates a new RA resource on the BWP1206 (initial BWP).

FIG. 13 illustrates a block diagram of a node for wirelesscommunication, in accordance with various aspects of the presentapplication. As shown in FIG. 13, a node 1300 may include a transceiver1320, a processor 1326, a memory 1328, one or more presentationcomponents 1334, and at least one antenna 1336. The node 1300 may alsoinclude an RF spectrum band module, a base station communicationsmodule, a network communications module, and a system communicationsmanagement module, input/output (I/O) ports, I/O components, and powersupply (not explicitly shown in FIG. 13). Each of these components maybe in communication with each other, directly or indirectly, over one ormore buses 1340. In one implementation, the node 1300 may be a UE or abase station that performs various functions described herein, forexample, with reference to FIGS. 1 through 12.

The transceiver 1320 having a transmitter 1322 (e.g.,transmitting/transmission circuitry) and a receiver 1324 (e.g.,receiving/reception circuitry) may be configured to transmit and/orreceive time and/or frequency resource partitioning information. In someimplementations, the transceiver 1320 may be configured to transmit indifferent types of subframes and slots including, but not limited to,usable, non-usable and flexibly usable subframes and slot formats. Thetransceiver 1320 may be configured to receive data and control channels.

The node 1300 may include a variety of computer-readable media.Computer-readable media can be any available media that can be accessedby the node 1300 and include both volatile and non-volatile media,removable and non-removable media. By way of example, and notlimitation, computer-readable media may comprise computer storage mediaand communication media. Computer storage media includes both volatileand non-volatile, removable and non-removable media implemented in anymethod or technology for storage of information such ascomputer-readable.

Computer storage media includes RAM, ROM, EEPROM, flash memory or othermemory technology, CD-ROM, digital versatile disks (DVD) or otheroptical disk storage, magnetic cassettes, magnetic tape, magnetic diskstorage or other magnetic storage devices. Computer storage media doesnot comprise a propagated data signal. Communication media typicallyembodies computer-readable instructions, data structures, programmodules or other data in a modulated data signal such as a carrier waveor other transport mechanism and includes any information deliverymedia. The term “modulated data signal” means a signal that has one ormore of its characteristics set or changed in such a manner as to encodeinformation in the signal. By way of example, and not limitation,communication media includes wired media such as a wired network ordirect-wired connection, and wireless media such as acoustic, RF,infrared and other wireless media. Combinations of any of the aboveshould also be included within the scope of computer-readable media.

The memory 1328 may include computer-storage media in the form ofvolatile and/or non-volatile memory. The memory 1328 may be removable,non-removable, or a combination thereof. Exemplary memory includessolid-state memory, hard drives, optical-disc drives, and etc. Asillustrated in FIG. 13, The memory 1328 may store computer-readable,computer-executable instructions 1332 (e.g., software codes) that areconfigured to, when executed, cause the processor 1326 to performvarious functions described herein, for example, with reference to FIGS.1 through 12. Alternatively, the instructions 1332 may not be directlyexecutable by the processor 1326 but be configured to cause the node1300 (e.g., when compiled and executed) to perform various functionsdescribed herein.

The processor 1326 (e.g., having processing circuitry) may include anintelligent hardware device, e.g., a central processing unit (CPU), amicrocontroller, an ASIC, and etc. The processor 1326 may includememory. The processor 1326 may process the data 1330 and theinstructions 1332 received from the memory 1328, and information throughthe transceiver 1320, the base band communications module, and/or thenetwork communications module. The processor 1326 may also processinformation to be sent to the transceiver 1320 for transmission throughthe antenna 1336, to the network communications module for transmissionto a core network.

One or more presentation components 1334 presents data indications to aperson or other device. Exemplary presentation components 1334 include adisplay device, speaker, printing component, vibrating component, andetc.

From the above description, it is manifested that various techniques maybe used for implementing the concepts described in the presentapplication without departing from the scope of those concepts.Moreover, while the concepts have been described with specific referenceto certain implementations, a person of ordinary skill in the art wouldrecognize that changes may be made in form and detail without departingfrom the scope of those concepts. As such, the described implementationsare to be considered in all respects as illustrative and notrestrictive. It should also be understood that the present applicationis not limited to the particular implementations described above, butmany rearrangements, modifications, and substitutions are possiblewithout departing from the scope of the present disclosure.

What is claimed is:
 1. A User Equipment (UE) comprising: one or morenon-transitory computer-readable media having computer-executableinstructions embodied thereon; and at least one processor coupled to theone or more non-transitory computer-readable media, and configured toexecute the computer-executable instructions to: receive DownlinkControl Information (DCI) via a Physical Downlink Control Channel(PDCCH) when performing a first Random Access (RA) procedure on a firstBandwidth Part (BWP), the DCI including a BWP switching indication; andperform at least one of a plurality of procedures in response to the BWPswitching indication, the procedures comprising: stopping the first RAprocedure on the first BWP and initiating a second RA procedure on asecond BWP indicated by the BWP switching indication; and ignoring theBWP switching indication to continue with the first RA procedure.
 2. TheUE of claim 1, wherein the procedures further comprise: continuing withthe first RA procedure on the first BWP after ignoring the BWP switchingindication.
 3. The UE of claim 1, wherein the procedures furthercomprise: continuing with the first RA procedure on an initial BWP afterignoring the BWP switching indication, wherein the initial BWP isindicated by system information from a base station.
 4. The UE of claim1, wherein the procedures further comprise: performing the second RAprocedure on the second BWP by using a group of RA parameters withconfigured values and using a group of UE variables with reset values.5. The UE of claim 4, wherein the group of UE variables comprises atleast one of a preamble counter and a power ramping counter.
 6. The UEof claim 1, wherein the procedures further comprise: initiating thesecond RA procedure on the second BWP when the second BWP is configuredwith an RA resource.
 7. The UE of claim 1, wherein the second BWP isconfigured with a Dedicated-Scheduling Request (D-SR) resource, and theprocedures further comprise: performing a Scheduling Request (SR)procedure on the second BWP by using the D-SR resource.
 8. The UE ofclaim 1, wherein the procedures further comprise: ignoring the BWPswitching indication when the second BWP is not configured with an RAresource.
 9. The UE of claim 1, wherein the procedures further comprise:ignoring the BWP switching indication when the second BWP is configuredwith an RA resource.
 10. The UE of claim 1, wherein the proceduresfurther comprise: initiating the second RA procedure on an initial BWPwhen the second BWP is not configured with an RA resource, wherein theinitial BWP is indicated by system information from a base station. 11.A method comprising: receiving, by a User Equipment (UE), DownlinkControl Information (DCI) via a Physical Downlink Control Channel(PDCCH) when the UE performs a first Random Access (RA) procedure on afirst Bandwidth Part (BWP), wherein the DCI includes a BWP switchingindication; and performing, by the UE, at least one of a plurality ofprocedures in response to the BWP switching indication, the procedurescomprising: stopping the first RA procedure on the first BWP andinitiating a second RA procedure on a second BWP indicated by the BWPswitching indication; and ignoring the BWP switching indication tocontinue with the first RA procedure.
 12. The method of claim 11,wherein the procedures further comprise: continuing with the first RAprocedure on the first BWP after ignoring the BWP switching indication.13. The method of claim 11, wherein the procedures further comprise:continuing with the first RA procedure on an initial BWP after ignoringthe BWP switching indication, wherein the initial BWP is indicated bysystem information from a base station.
 14. The method of claim 11,wherein the procedures further comprise: performing the second RAprocedure on the second BWP by using a group of RA parameters withconfigured values and using a group of UE variables with reset values.15. The method of claim 14, wherein the group of UE variables comprisesat least one of a preamble counter and a power ramping counter.
 16. Themethod of claim 11, wherein the procedures further comprise: initiatingthe second RA procedure on the second BWP when the second BWP isconfigured with an RA resource.
 17. The method of claim 11, wherein thesecond BWP is configured with a Dedicated-Scheduling Request (D-SR)resource, and the procedures further comprise: performing a SchedulingRequest (SR) procedure on the second BWP by using the D-SR resource. 18.The method of claim 11, wherein the procedures further comprise:ignoring the BWP switching indication when the second BWP is notconfigured with an RA resource.
 19. The method of claim 11, wherein theprocedures further comprise: ignoring the BWP switching indication whenthe second BWP is configured with an RA resource.
 20. The method ofclaim 11, wherein the procedures further comprise: initiating the secondRA procedure on an initial BWP when the second BWP is not configuredwith an RA resource, wherein the initial BWP is indicated by systeminformation from a base station.